The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Design database
|
|
Identify organisational and task requirements to confirm scope and functionality of database design, including data redundancy Completed |
Evidence:
|
Develop a logical data model to identify and classify data into types in accordance with organisational and task requirements Completed |
Evidence:
|
Select appropriate digital application/platform according to organisational and task requirements, available resources, and required scope and functionality of database Completed |
Evidence:
|
Create and document proposed database structure, and share with appropriate personnel in accordance with organisational policies and procedures Completed |
Evidence:
|
Seek feedback on proposed database design from appropriate personnel Completed |
Evidence:
|
Develop database
|
|
Set field attributes according to data type and link databases by a common field in accordance with database application usage Completed |
Evidence:
|
Assign primary key to uniquely identify data Completed |
Evidence:
|
Assign foreign keys to establish associations between data, in accordance with organisational and task requirements Completed |
Evidence:
|
Use software functions and formulae to meet organisational and task requirements Completed |
Evidence:
|
Create password and access system according to organisational policies and procedures relating to data security Completed |
Evidence:
|
Access and use application help functions to overcome intermediate-level issues with database design and production, where required Completed |
Evidence:
|
Develop queries, forms and reports
|
|
Identify information output, database tables to be use and report layout, in accordance with task requirements Completed |
Evidence:
|
Identify data groupings, search and sort criteria, in accordance with task requirements Completed |
Evidence:
|
Run reports and queries to confirm that results and formulae produce required data Completed |
Evidence:
|
Modify reports to include or exclude additional requirements, where necessary Completed |
Evidence:
|
Test and finalise database
|
|
Populate database with sample dataset for testing, meeting organisational requirements for speed and accuracy Completed |
Evidence:
|
Assess and document effectiveness of data relationships, query forms and reports, assessing against organisational and task requirements Completed |
Evidence:
|
Document and address any errors in database design Completed |
Evidence:
|
Name and store database in accordance with organisational policies and procedures relating to data security, and exit the application without data loss or damage Completed |
Evidence:
|
Confirm database readiness with appropriate personnel Completed |
Evidence:
|
Identify organisational and task requirements to confirm scope and functionality of database design, including data redundancy Completed |
Evidence:
|
Develop a logical data model to identify and classify data into types in accordance with organisational and task requirements Completed |
Evidence:
|
Select appropriate digital application/platform according to organisational and task requirements, available resources, and required scope and functionality of database Completed |
Evidence:
|
Create and document proposed database structure, and share with appropriate personnel in accordance with organisational policies and procedures Completed |
Evidence:
|
Seek feedback on proposed database design from appropriate personnel Completed |
Evidence:
|
Set field attributes according to data type and link databases by a common field in accordance with database application usage Completed |
Evidence:
|
Assign primary key to uniquely identify data Completed |
Evidence:
|
Assign foreign keys to establish associations between data, in accordance with organisational and task requirements Completed |
Evidence:
|
Use software functions and formulae to meet organisational and task requirements Completed |
Evidence:
|
Create password and access system according to organisational policies and procedures relating to data security Completed |
Evidence:
|
Access and use application help functions to overcome intermediate-level issues with database design and production, where required Completed |
Evidence:
|